Automatic self configuration of client-supervisory nodes

ABSTRACT

A system of controllers act as nodes on a network. One controller is identified as a supervisory node and the remaining controllers are identified as client nodes with the supervisory node and each client node broadcasting a default identifier, created at the time of manufacture, in a default domain. The default identifiers from the client nodes are received and ranked at the supervisory node according to a characteristic in the identifier. A network address is created at the supervisory node for each client node and broadcast in the default domain to all client nodes. The client nodes receive all network addresses but only recognize and internalize the network address corresponding to a specific client node. Control information is then communicated between nodes utilizing subnet and node addressing.

BACKGROUND OF THE INVENTION

The present invention relates generally to controls and morespecifically to communication between control devices or nodes connectedin a network. Networks were traditionally used in large computer systemswhere the communication protocols were designed and optimized for largeamounts of data between computers. The declining cost of microprocessorseventually allowed their use in inexpensive controllers and controldevices. However, the communication protocols used in large dataprocessing systems did not meet the unique requirements of controlnetworks which typically require frequent communication between devices,short message formats, peer to peer communication and costs consistentwith the use of low cost control devices. These requirements lead to thedevelopment of protocols designed for use in control networks ratherthan for use in data processing networks. The applications that use suchcontrol networks are many and varied. For example, the controls may berelated to heating ventilating and air conditioning (HVAC) applications,lighting control applications, building security applications and manyother applications. The present invention is not limited by the natureof the application. Many control manufacturers make control devices thatcommunicate using a particular communication technology, one example ofa communication technology is the LonWorks System as provided by theEchelon Corporation. In the simplest installation the control node istypically connected to a single control device in a stand-aloneinstallation. In larger more complex installations a single Supervisorynode may send messages to a number of Client nodes and the Client nodesmay send messages to the Supervisory node as well as to other Clientnodes. In order to initially establish this communication between aSupervisory node and a Client node, it typically requires a techniciantrained in the use of network tools or configuration tools to bephysically present at the network installation site and to assignaddresses to the nodes to allow communications between nodes and toconfigure the nodes. A network installation tool maintains a database ofthe device addresses for the network assigns the device addresses.Device addresses typically consist of three components: a domain addressor ID, subnet ID, and node ID. Therefore, a technician trained in theuse of the configuration tool will need to travel to the location of thenetwork installation, coordinate the visit with the availability ofother trade persons, e.g. an electrician, at the location and spend timeat the location in performing the address assignment and configurationtasks. Depending on how the communication technology is implemented,these tasks may further require visiting each node location to set dipswitches or to depress a button as part of the process. In addition tothe technician tasks related to simply establishing communicationbetween the nodes there are additional technician tasks. For example,many control nodes can also be configured to be capable of communicationand interaction with multiple other nodes of similar design, providingsystem control and sharing of selected information through the systemusing a communication technique called “binding”. Establishing theserelationships between nodes is also accomplished with a configurationtool at the installation site.

The processes just described obviously increases the cost of a networkinstallation.

Self-configuration has been proposed in the past but is usually limitedto a very small subset of information and does not meet the need ofself-configuration for control networks. Thus a need exists for anetwork system that will be automatically self configured.

SUMMARY OF THE INVENTION

The present invention solves these and other needs by providing in afirst aspect a system of controllers acting as nodes on a network andproviding automatic self-configuration. One controller is identified asa supervisory node and the remaining controllers are identified asclient nodes with the supervisory node and each client node broadcastinga default identifier in a default domain. The default identifiers arecreated at the time of manufacture of the node microprocessor. Thedefault identifiers from the client nodes are received and rankedaccording to a characteristic in the identifier at the supervisory node.A network address is created at the supervisory node for each clientnode and broadcast in the default domain to all client nodes. The clientnodes receive all network addresses but only recognize and internalizethe network address corresponding to a specific client node. Controlinformation is then communicated between nodes utilizing subnet and nodeaddressing.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a single boiler arrangement.

FIG. 2 is a functional block diagram of a Boiler Interface Controller(BIC) according to the principles of that invention.

FIG. 3 is a functional block diagram of a Human Interface Panel (HIP)for use with one BIC according to the principles of the HIP invention.

FIG. 4 is a functional block diagram of a Human Interface Panel for usewith a Sequencer according to the principles of the HIP invention.

FIG. 5 is a contextual software drawing of the Sequencer and modularboiler system of FIG. 4.

FIG. 6 is an illustration of certain details of the Sequencer of FIGS. 4and 5.

FIG. 7a and FIG. 7b are a diagram illustrating an overview of theoperation of the BIC invention of FIG. 2.

FIG. 8 is a flowchart diagram illustrating the operation of the BICinvention in the idle mode, mode 0.

FIG. 9a is a flowchart illustrating the operation of the BIC inventionin the water flow evaluation mode, mode 1.

FIG. 9b is a flowchart illustrating the operation of the BIC inventionin the water flow failure mode, mode 1A.

FIG. 9c is a flowchart illustrating the operation of the BIC inventionin a water flow test routine, T1.

FIG. 10a is a flowchart illustrating the operation of the BIC inventionin the low gas pressure evaluation mode, mode 2.

FIG. 10b is a flowchart illustrating the operation of the BIC inventionin the low gas pressure failure mode, mode 2A.

FIG. 10c is a flowchart illustrating the operation of the BIC inventionin a low gas pressure test routine, T2.

FIG. 11a is a flowchart illustrating the operation of the BIC inventionin the low air evaluation mode, mode 3.

FIG. 11b is a flowchart illustrating the operation of the BIC inventionin the low air failure mode, mode 3A.

FIG. 11c is a flowchart illustrating the operation of the BIC inventionin a low air test routine, T4.

FIG. 12a is a flowchart illustrating the operation of the BIC inventionin the blocked drain evaluation mode, mode 4.

FIG. 12b is a flowchart illustrating the operation of the BIC inventionin the blocked drain failure mode, mode 4A.

FIG. 12c is a flowchart illustrating the operation of the BIC inventionin a blocked drain test routine, T4.

FIG. 13a is a flowchart illustrating the operation of the BIC inventionin the prepurge evaluation mode, mode 5.

FIG. 13b is a flowchart illustrating the operation of the BIC inventionin the soft lockout mode, mode 5A.

FIG. 14a is a flowchart illustrating the operation of the BIC inventionin the ignition evaluation mode, mode 6.

FIG. 14b is a flowchart illustrating the operation of the BIC inventionin the flame failure mode, mode 6A.

FIG. 14c is a flowchart illustrating the operation of the BIC inventionin a flame failure test routine, T5.

FIG. 15 is a flowchart illustrating the operation of the BIC inventionin the boiler on evaluation mode, mode 7.

FIG. 16 is a flowchart illustrating the operation of the BIC inventionin the heat mode, mode 8.

FIG. 17 is a flowchart illustrating the operation of the BIC inventionin the post purge preparation mode, mode 9A.

FIG. 18 is a flowchart illustrating the operation of the BIC inventionin the post purge mode, mode 9B.

FIG. 19 is a functional block diagram of a network which providesautomatic self-configuration of controllers acting as nodes on a networkaccording to the principles of that invention.

FIGS. 20a through 20 d are flowcharts illustrating a portion of theoperation of the HIP invention of FIGS. 3 and 4.

FIG. 21 is an example of a menu for an operator interface according tothe prior art.

FIG. 22 is an example of a menu according to the principles of the HIPinvention of FIGS. 3 and 4.

DESCRIPTION OF THE PREFERRED EMBODIMENT

A single boiler arrangement is shown in FIG. 1 including watercirculating pump 12, primary heat exchanger 14 and secondary heatexchanger 16 which utilizes combustion waste heat 17. Recirculatingvalve 20 insures that a minimum water temperature is maintained in theboiler. Supply or outlet water temperature sensor 22, return or inletwater temperature sensor 24, and bypass water temperature sensor 26 arealso shown. A variable firing rate is provided for the boiler byvariable frequency drive (VFD) combustion/purge blower 18. Othertechniques for providing a variable firing rate could be used.

A boiler interface controller (BIC) for use in a single boilerarrangement according to the teachings of the present invention is shownin the figures and generally designated 10. BIC 10 is shown forinterfacing with a flame safety controller 30, which provides therequired flame safety functions.

BIC 10 in the preferred embodiment employs a Neuron (a registeredtrademark of Echelon Corp.) microprocessor that is well adapted tobuilding control system networks.

The Neuron Chip Distributed Communications and Control Process includesthree 8-bit pipelined processors for concurrent processing ofapplication code and network packets. The 3150 contains 512 bytes ofin-circuit programmable EEPROM, 2048 bytes of static Ram, and typically32768 bytes of external EPROM memory. The 3150 typically uses a 10 MHzclock speed. Input/Output capabilities are built into themicroprocessor. The LonWorks® firmware is stored in EPROM and allowssupport of the application program. The Neuron Chip performs network andapplication-specific processing within a node. Nodes typically containthe Neuron Chip, a power supply, a communications transceiver, andinterface electronics.

The Neuron Microprocessor is part of the LonWorks® technology that is acomplete platform for implementing control network systems. The LonWorksnetworks consist of intelligent devices or nodes that interact with eachother, communicating over pre-defined media using a message controlprotocol.

The processor is programmed using the LonBuilder Workstation hardwareand software in Neuron-C (the language for the Neuron chip). Thefirmware application is developed using the LonBuilder developmentstation. Typically the application generated by the LonBuilderDevelopment software environment is compiled and stored in the customEPROM for use by the node during execution. Certainly othermicroprocessors may be employed, but the programming will have to beappropriately modified.

Various control modules are implemented in firmware in BIC 10 as isshown in a single boiler configuration in FIG. 2 including boilertemperature control module 28, bypass temperature control module 32, andstatus and mode control module 34. BIC 10 is shown interfacing tovarious elements of a boiler control system for controlling a boiler forheating a medium which is typically water. Temperature control module 28receives signal 36 from sensor 22 located in the boiler supply water,signal 38 from sensor 24 located in the boiler return water, and signal44 from sensor 42 located in outdoor air. Boiler temperature controlmodule 32 also provides for receiving a setpoint signal related to adesired control set point signal. Bypass temperature control module 32receives signal 40 from bypass temperature sensor 26 and provides signal46 to bypass valve 20. Module 32 provides for receiving a set pointsignal.

BIC 10 as well as the Human Interface Panel and the Fault TolerantMulti-Boiler Sequencer described herein may be prepared for a particularboiler installation using a configuration tool which is external to BIC10.

Flame safety controller 30 provides an ignition command 54 to ignitionelement 56, a gas valve command 58 to gas valve 60 and a variablefrequency drive (VFD) command 62 to variable speed combustion/purgemotor 18.

BIC 10 provides a request for heat signal 52 to flame safety controller30 through boiler safety devices but BIC 10 does not perform flamesafety functions. While BIC 10 does not perform flame safety functions,it does receive status information from boiler safety switches 66 andother devices. Typical safety switches relate to proving water flow ispresent, supply gas pressure is not too high or too low, combustionpurge pressure is not to high or too low and a condensate drain is notblocked. These boiler safety status signals may be provided by anauxiliary contact (not shown) for each of contact closures 66 related toeach of the four (4) safety switches. Safety switch status signals wouldbe provided on conductors 68. The order in which such auxiliary contactsare electrically connected is to be coordinated with the order of themodes described herein. Status and mode control module 34 of BIC 10 inits preferred form receives signal 70 as to the “on” or “off” status ofignition element 56, signal 72 as to the “on” or “off” status of gasvalve 60, signal 64 as to the status of combustion/purge fan 18, signal76 as to the status of pump 12 and signal 78 as to the status of flamesafety controller 30. Boiler temperature control module 28 of BIC 10provides a VFD speed control signal 74 to variable speedcombustion/purge motor 18.

Now that certain aspects of BIC 10 have been disclosed, the operationcan be set forth and appreciated. Boiler temperature control module 28utilizes supply water temperature signal 36, outdoor air temperaturesignal 44 (optional), the setpoint of module 28 and an internalalgorithm to cause an internal call for heat condition within BIC 10 andto issue external request for heat signal 52. As an alternative, a spacetemperature sensor could have been connected as an input to module 28 toallow the internal call for heat condition to be a function of spacetemperature.

The operation of BIC 10 is best understood by reference to the statediagram shown in FIG. 7a and FIG. 7b, which identifies the modes andtransitions between modes and then by reference to a flowchart thatprovides the details of a specific mode. In general, the BIC mode statetransition diagram is intended to be used in a task scheduledenvironment. The scheduling mechanism should schedule the statetransition software to run on a regular nominal 1-second interval.

In the preferred embodiment, the state information is stored betweentask executions in the nvoData.Mode variable to maintain the last knownboiler state. This will allow the software executive to multi-task andperform other operations between successive state transition tasks, andallow other functions to be performed without loosing the last knownstate of the boiler. This allows efficient use of the hostmicroprocessor and computer system resources.

The various modes are designated in FIGS. 7a and 7 b by a referencenumeral corresponding to the mode designation preceded by the numeral 7,for example mode 1 is designated as 7-1. For simplicity it may also bereferred to herein as Mode 1. With reference to FIG. 7a, in Mode 0, Idlemode, the BIC has no call for heat and is awaiting a signal to startheating. If the call for heat is on, then initiate transition 7-12 tomode 1, water flow evaluation. The order of electrical wiring of boilersafety switches, for example water flow and gas pressure, is tocorrespond with the order of the modes related to these switches.

Transitions out of Mode 1: If the call for heat is off, then initiatetransition 7-14 to mode 0. If the Low Water Flow input is on and hasbeen on for a predetermined time, then initiate transition 7-16 to Mode1A, Water Flow Fail Mode. If the Low Water flow input is satisfactory,then initiate transition 7-18 to Mode 2, Gas Pressure Evaluation.

Transitions out of Mode 1A: If the call for heat is off, then initiatetransition 7-20 to mode 0. If the Low Water flow input returns to off,then initiate transition 7-22 to Mode 1.

Transitions out of Mode 2: If the call for heat is off, then initiatetransition 7-24 to mode 0. If the Low Water Flow input is low, theninitiate transition 7-26 to Mode 1A. If The Gas Pressure Fail input isON, then initiate transition 7-28 to mode 2A Gas Pressure Fail. If thegas pressure fail input is off and all tests are complete, then initiatetransition 7-30 to mode 3, Air Pressure Evaluation.

Transitions out of Mode 2A: If the call for heat is off, then initiatetransition 7-32 to mode 0. If the Gas Pressure Fail input is OFF, theninitiate transition 7-34 to Mode 2.

Transitions out of mode 3: If the call for heat is off, then initiatetransition 7-36 to mode 0. If the Low Water Flow input is low, theninitiate transition 7-38 to Mode 1A. If The Gas Pressure Fail input isON, then initiate transition 7-40 to mode 2A. If the Low air input isON, then initiate transition 7-42 to mode 3A Low Air Fail. If Low airinput is off, and all tests are complete, then initiate transition 7-44to Mode 4 Block Drain.

Transitions out of Mode 3A: If the call for heat is off, then initiatetransition 7-46 to mode 0. If the Low air input is off then initiatetransition 7-48 to Mode 3.

Transitions out of Mode 4: If the call for heat is off, then initiatetransition 7-50 to mode 0. If the Low Water Flow input is on, theninitiate transition 7-52 to Mode 1A. If The Gas Pressure Fail input ison, then initiate transition 7-54 to mode 2A. If the Low air input ison, then initiate transition 7-56 to mode 3A. If Block drain input ison, then initiate transition 7-58 to Mode 4A Block Drain. If Block draininput is off, and all tests are complete then initiate transition 7-60to Mode 5, Prepurge.

Transitions out of Mode 4A: If the call for heat is off, then initiatetransition 7-62 to mode 0. If the Low air input is off then initiatetransition 7-64 to Mode 4.

Transitions out of Mode 5: If the call for heat is off, then initiatetransition 7-66 to mode 0. If the Low Water Flow input is on, theninitiate transition 7-68 to Mode 1A. If The Gas Pressure Fail input ison, then initiate transition 7-70 to mode 2A. If the Low air input ison, then initiate transition 7-72 to mode 3A. If Block drain input ison, then initiate transition 7-74 to Mode 4A Block Drain. Refer toflowcharts for information on transition 7-76 to Mode 5A, Soft Lockoutand transition 7-78 to Mode 6, Ignition Evaluation.

Transition out of Mode 5A: If the call for heat is off, then initiatetransition 7-82 to Mode 0. Refer to flowcharts for conditions fortransition 7-80. Transitions out of Mode 6: Refer to flow charts forconditions for transition 7-88 to Mode 5A, transition 7-92 to Mode 5A,transition 7-90 to Mode 6A, transition 7-86 to 60 Sec timer andtransition 7-94 to Mode 7 Boiler On Evaluation.

Transitions out of Mode 6A: If the call for heat is off, then initiatetransition 7-96 to mode 0. If the Low Water Flow input is on, theninitiate transition 7-98 to Mode 1A

Transitions out of Mode 7: Refer to flow charts for conditions fortransition 7-100 to Mode 9A, Post Purge Prepare, and transition 7-102 toMode 8, Heat.

Transitions out of Mode 8: Refer to flow charts for transition 7-104 toMode 9, Bypass Temp Control, and transition 7-110 to Mode 9A Post PurgePrepare. 8A, Bypass Temperature Control represents the control of valve20 from bypass temperature 26 and bypass temperature control 32.

Transitions out of Mode 9A: Refer to flow chart for transition 7-112 toMode 9B, Post Purge.

Transitions out of Mode 9B: When Post Purge timer expires, initiatetransition to Mode 0, Idle.

By way of example, if no call for heat exists, then BIC 10 is in an“Idle” mode, mode 0 as illustrated in FIG. 8. When a call for heatcondition occurs, BIC 10 selects a first evaluation mode within anordered succession of evaluation modes. In the preferred form, the firstevaluation mode is the Water Flow Evaluation, mode 1 as illustrated inFIG. 9a. The water flow evaluation mode may result in BIC 10 returningto the Idle mode if a call for heat no longer exists, or initiating anext evaluation mode, i.e., the Gas Pressure Evaluation, mode 2 asillustrated in the FIG. 10a. In the event that water flow is not provenin mode 1, then a water flow failure mode, mode 1A as shown in FIG. 9bis initiated. Mode 1A provides for a predetermined number of cycles,e.g., 5 cycles or 5 seconds. If water flow is not satisfactorily provenin this time, then a water flow test routine is initiated which resultsin water flow failure shutdown of the boiler. An understanding of theother modes may be had by reference to the appropriate flowcharts.

A particular embodiment of BIC 10 has been described and many variationsare possible. By way of example, and not by way of limitation, BIC 10 isuseful with boilers that employ a greater number or a lesser number ofboiler safety switches, boilers that do not have a variable firing rateand boilers that are not condensing type boilers and therefore do notuse the system bypass valve.

Although the BIC has adequate evidence for mode changes, it is not to bedepended on for any flame safety control functions. However, theinformation that the BIC has will be highly useful information forperformance evaluation and troubleshooting of boiler systems.

In the event of a boiler failure the use of BIC 10 will permit a boilerservice person to quickly diagnose many problems. Using only typicalportable testing devices, e.g. a volt-ohm-meter, a service person candetermine at what point in the boiler operating sequence a problemexists. In addition, more sophisticated diagnostic tools such as alaptop or handheld device may be used to query nodes and perform otherdiagnostic tests. That is, through the monitoring of the modes, oroutputs, or alarms of BIC 10, the service person can easily isolate theproblem and take action to correct the problem and restore boileroperation.

The operation of BIC 10 has been explained by describing its applicationto a boiler for a heating system. BIC 10 is also very useful in thecontrol of water heaters. Certain features of BIC 10, for example thereset of the water temperature setpoint as a function of the outdoor airtemperature would not be used in the water heater application.

A human interface panel (HIP) for use with BIC 10 is shown in thefigures and generally designated 100. HIP 100 will be explained byreference to its use with BIC 10, but it is to be understood that theprinciples will be useful with any boiler system that is arranged totake advantage of the features of the HIP of the present invention. HIP100 in a single boiler configuration with BIC 10 is illustrated in FIG.3. Where inputs to BIC 10 from sensors are designated with a referencenumeral and a letter, e.g., return water temperature 24 a indicatingthat a sensor for the same purpose was described with regard to FIG. 2.Temperature control module 28 a receives signal 36 a from sensor 22 alocated in the boiler supply water, signal 38 a from sensor 24 a locatedin the boiler return water, and signal 44 a from sensor 42 a located inoutdoor air. BIC 10 also provides for receiving a setpoint signalrelated to a desired control setpoint signal. Bypass temperature controlmodule 32 a receives signal 40 a from bypass temperature sensor 26 a andprovides signal 46 a to bypass valve 20 a.

HIP 100 in the preferred form includes arbitration logic module 102having a number of status inputs that will be further explained,transceiver 106 and a command display device (CDD) 104. According to theprinciples of the HIP invention, arbitration logic module 102 receivesstatus inputs from BIC 10 and other status devices including boilersafety switch status 68 a, ignition device status signal 70 a, gas valvestatus signal 72 a, combustion/purge fan status 64 a, pump status 76 a,flame safety controller status signal 78 a, temperature control status130, bypass status 132, and bypass resynch status 134. For simplicity,only representative inputs to arbitration logic 102 have been shown inFIG. 3. In operation, the arbitration logic is implemented by readingall inputs to arbitration logic module 102 including the following:request for heat, sys disable, sys init, emergency, factory test, hightemp, freeze protect, hvac emerg, hvac off, water flow safety, gaspressure safety, high/low gas pressure safety, low air pressure safety,block drain safety, pre-purge, ignition ON, gas valve ON, flame fail,post-purge, sequencer, fire low, fire mid, fire hi, number of stages,total stages, staged firing rate, min firing timer.

After reading all inputs, arbitration logic 102 then processes thereadings according to the structure shown in the flow chart of FIG. 20.Arbitration logic module 102 provides output 108 to transceiver 106which provides signal 110 to CDD 104. Arbitration logic module 102 andtransceiver 106 are located at the boiler and may be in the sameenclosure as BIC 10 while CDD 104 may be located at a distance from theboiler. CDD 104 in the preferred form includes an Echelon transceiver112, Echelon Neuron 3120 processor 114, microprocessor 116,configuration memory 118, memory 120, keypad 122 and LCD screen display124. Neuron processor 114 periodically, e.g., once per sec, requests thestatus of a specific status variable using the address andidentification of the device and status variable. Arbitration logicmodule 102 responds with arbitration encoded signal 110 which isreceived thru transducer 112 and stored in a communications buffer inNeuron processor 114. Microprocessor 116 processes and decodes themessage to user friendly text and buffers and displays the message ondisplay 124.

Permanent configuration information on identification structure andaddress of information is stored permanently in electrically erasablememory or flash memory 120. Keypad 122 is used to select information fordisplay and to move to different displays, e.g. from the status ofindividual boilers within a group of boilers to individual status valueswithin a specific boiler.

The HIP of the present invention is a single status variable that candisplay the current status of an individual boiler or a system thatincludes a group of boilers. The display includes status informationsuch as single stage firing status, multiple stage firing status, safetyconditions, pre-purge, post purge, unknown safety, ignition evaluation,and post purge preparation. In addition the HIP provides monitoring offlame safety controller status, and active management ofnon-flame-safety mode changes in a real time temperature controlenvironment. The HIP invention in the specific embodiment shown utilizesthe Status_Mode display variable. This technique consolidates criticalsystem functions and error information in one efficient variablestructure using the LonWorks protocol to transfer information from theboiler devices. This data structure can be transferred to a low costpeer to peer device through the Echelon bus. Information on the use ofthe Lonworks System is available from the Echelon Corporation, 4015Miranda Avenue, Palo Alto, Calif. 94304, USA. While certain specificembodiments of the present invention are described with reference to theLonWorks System, it is not intended that the invention be so limited.Other processors and communication protocols could be used.

The use of the HIP with a single boiler has been described. In addition,the HIP may be used in a multiple boiler system where a number ofindividual boilers are installed with the pumping and water pipingarranged to provide for common system return water temperature, commonsystem supply temperature and common system bypass temperature. The useof HIP 100 in a multiple boiler embodiment is illustrated in FIG. 4where BIC 1 interfaces to Boiler 1 and BIC X interfaces to Boiler X. Theuse of HIP 100 with multiple boilers includes the use a sequencingcontroller 200, the operation of which is more completely describedherein.

In the multiple boiler embodiment BIC 10 is configured with modules asshown in FIG. 4 including system temperature control module 202, outdoorair reset module 210, analog stage control module 216, stager module204, sequencer control module 222, stage status module 224, runtime modestage control module 226, pump controller 227, system bypass controlmodule 250 and network interface 228. In operation, temperature controlmodule 202 and stager module 204 both receive system return watertemperature from sensor 206 and system supply temperature from sensor208. Outdoor air reset module 210 receives outdoor air temperature fromsensor 212 and provides a reset setpoint to system temperature controlmodule 202. System temperature control module 202 provides request forheat signal 276 to pump controller 227 and, to arbitration logic module102 a as well as freeze protection signal 274 to arbitration logicmodule 102 a. Analog stage control module 216 receives temperaturecontrol information signal 218 from and provides system firing ratesignal 220 to sequencer control module 222 and to arbitration logicmodule 102 a. Stager module 204 provides a requested number of stagessignal 238 to sequencer control module 222 and to arbitration logicmodule 102 a based on a rate of change of the temperature differencebetween the supply temperature 208 and return temperature 206 and othervariables. Stage status module 224 receives information from BIC 1 andBIC X. System bypass control module 250 receives a system bypasstemperature from sensor 252 and provides bypass status 256 and systemresynch status 258. Multiple boiler arbitration logic module 102 a has anumber of additional inputs including system factory test 264, systemwaterflow 266, manual 268, low gas pressure 270, pump status 272, freezeprotection 274, disabled mode 278 and emergency mode 280. Forsimplicity, only representative inputs are shown. Arbitration logicmodule 102 a responds through a network interface module (not shown)with arbitration encoded signal 282 which is received by networkinterface module 228 and provided to CCD 104. The functioning of CCD 104in the multiple boiler implementation is as described under the HIP 100description for the single boiler embodiment and includes the ability todisplay status information from a multiple boiler system as well asindividual boilers within the multiple boiler system.

The single status variable from the Temperature controller allows themonitor boiler system status displayed in a hard real time, statemachine task environment that will not require uninterrupted andsequential access to conditions.

In the preferred form, unique status modes are displayed as shown inTable 1. The term status mode or application mode may be usedinterchangeably. The meaning of the individual status modes will beapparent from the EnumType.

TABLE 1 EnumVal- DataType bice.txt EnumType ue STATUS_MODE START_UP_WAIT0 STATUS_MODE IDLE 1 STATUS_MODE WATER_FLOW_EVAL 2 STATUS_MODEAIR_PRES_EVAL 3 STATUS_MODE BLOCK_DRAIN_EVAL 4 STATUS_MODELOW_GAS_PRESS_EVAL 5 STATUS_MODE PRE_PURGE 6 STATUS_MODE IGNITION_EVAL 7STATUS_MODE BOILER_ON_EVAL 8 STATUS_MODE HEAT 9 STATUS_MODEWATER_FLOW_FAIL_MODE 10 STATUS_MODE AIR_PRESS_FAIL_MODE 11 STATUS_MODEBLOCK_DRAIN_FAIL_MODE 12 STATUS_MODE BLOCK_FLUE_FAIL_MODE 13 STATUS_MODELOW_GAS_PRESS_FAIL_MODE 14 STATUS_MODE FLAME_FAILURE_MODE 15 STATUS_MODESOFT_LOCK_OUT_FAIL_MODE 16 STATUS_MODE HEAT_MOD_FAIL_MODE 17 STATUS_MODEMANUAL 18 STATUS_MODE FACTORY_TEST 19 STATUS_MODE PUMP_ONLY 20STATUS_MODE EMERGENCY_MODE 21 STATUS_MODE DISABLED_MODE 22 STATUS_MODEHIGH_TEMP_MODE 23 STATUS_MODE OFF_MODE 24 STATUS_MODE SMOKE_EMERGENCY 25STATUS_MODE POST_PURGE 26 STATUS_MODE FREEZE_PROTECT_MODE 27 STATUS_MODEPOST_PURGE_PREPARE 28 STATUS_MODE FLOAT_OUT_SYNC 29 STATUS_MODEIDLE_MIN_DELAY 30 STATUS_MODE SPARE_MODE2 31 STATUS_MODE SEQ_HEAT_0STGS32 STATUS_MODE SEQ_HEAT_1STGS 33 STATUS_MODE SEQ_HEAT_2STGS 34STATUS_MODE SEQ_HEAT_3STGS 35 STATUS_MODE SEQ_HEAT_4STGS 36 STATUS_MODESEQ_HEAT_5STGS 37 STATUS_MODE SEQ_HEAT_6STGS 38 STATUS_MODESEQ_HEAT_7STGS 39 STATUS_MODE SEQ_HEAT_8STGS 40 STATUS_MODESEQ_HEAT_9STGS 41 STATUS_MODE SEQ_HEAT_10STGS 42 STATUS_MODESEQ_HEAT_11STGS 43 STATUS_MODE SEQ_HEAT_12STGS 44 STATUS_MODESEQ_HEAT_13STGS 45 STATUS_MODE SEQ_HEAT_14STGS 46 STATUS_MODESEQ_HEAT_15STGS 47 STATUS_MODE SEQ_HEAT_16STGS 48 STATUS_MODE HEAT_Low49 STATUS_MODE HEAT_MEDIUM 50 STATUS_MODE HEAT_HIGH 51

The HIP boiler status display variable structure is shown in Table 2.

TABLE 2 Example Data Field Field Field Name (Range) Length Data TypeDescription NvoBoilerStatus ApplicMode HEAT 1 byte ENUMERATION CurrentApplication Share: (See table 1 (BYTE) Mode of to be Polled From forlist of of type commanded to Boiler to HIP or Enumerations) STATUS_MODEthe boiler - See monitoring node Table 1 for possible values Additional. . . . . . . . . . . . fields Additional . . . . . . . . . . . . fields

The HIP provides access to all control boiler functionality such as modeprogression monitoring, pre-purge speed, pre-ignition speed control,Heat evaluation mode, and post purge ignition shutdown capabilities fromthe temperature control BIC. By proper boiler system design, all modemonitoring and transitions present in the BIC can be implemented withoutinterfering with the flame-safety controller's safety requirements. Inaddition, the BIC provide temperature control of multiple stages of ahigh efficiency condensing, automatic bypass control, modulating firingrate boiler at both the individual modular boiler level and systemsequencing level.

Now that the operation of HIP 100 has been set forth, many advantagescan be further set forth and appreciated:

Safety and Health Factor: Hot Water boilers, gas boilers, high-pressuresteam, and boiler devices are prone to very critical safety issues.Traditionally these safety issues are solved through extremely stringentregulations on boiler manufacturers concerning “flame safety” devicesand rigid safety mode analysis. One area that has not been exploited isto use the non-flame safety status of the boiler and display thisinformation to the user in an intelligent combination that providessafety diagnostic information, and allows monitoring of the boilers forcharacteristics of unsafe conditions (such as flame fail or repeatedattempts at ignition) that will allow tracking of problems before theystart. By making the status of the boiler modes and safety conditionsreadily available, safety is improved and the chance of injury due toboiler explosion is reduced. Safety and Health benefits are accruedthough addition system incorporation into the HIP display.

Cost: By using, in the preferred mode, the UNVT_Status_Mode displayvariable to transfer information from the boiler devices, significantcost reductions of interface can be achieved and realized byconsolidation of critical system functions and error information in onevery efficient variable structure. This data structure can betransferred to a low cost peer to peer device through the Echelon bus,which provides for interoperability, interoperability standards,cross-industry support, and low cost interface. By using fewer relays tointerface the information to traditionally expensive automation panels,and through the use of low cost displays, multiple display locations ofboiler status results are possible.

Ease of use: no Boiler operation knowledge is necessary, as allinformation is available “at a glance” from HIP main view screen. Thisergonomically pleasing display is easy and compelling for the user tointeract with and can easily be used to evaluate complete boiler systemstatus.

Ease of production: Due to the significantly reduced complexity of thedisplay and general-purpose interface of the display, the end devicecould be produced very inexpensively. Multiple HIP devices could beadded to the system as both a local and remote display. Subsets ofBoiler Data and System Data could be displayed from the local device orat a remote location such as the System engineers office, or the ChurchCustodians or Fast Food Restaurant Managers office.

Durability: Since there is no remote relay connections and wiring, thetraditionally expensive and complex remote status display is now verycost effective, and is supported by true 3^(rd) party interoperabilitywith a ubiquitous and commodity interface. Without the wide variety ofwiring and remote connections, the design is much more durable thanprevious

Interoperability—Since the boiler system preferred implementation isperformed on the Echelon LonWorks System, multi-vendor support, internetcommunication, cell phone access, and remote diagnostics, trending,database analysis, and support can be afforded through 3^(rd) partysolutions. By utilizing a non-flame safety device, the communicationsinterface is removed from the failure recovery and acknowledgmentmechanisms inherent in the protocol used for flame safety devices.

Convenience/Repair—by being aware of the operation and failure modes ofthe boiler, a repairperson would be able to save a trip or carry thecorrect part with them before making a service trip to the boilerinstallation. Careful inspection and monitoring of a boiler transitionof the status modes, and observation of the conditions up to the failurecan reveal the boiler operation condition with startling accuracy. TheHip and Boiler Interface units themselves are quite simple and lead toquick repair of failed units.

Efficiency: By observing the actual firing status and system operation,conclusions about the operational efficiency and number of stagesrequired to achieve stable control of heat transfer can be observeddirectly in real time from a remote location. By detailed observation ofthe boiler status and sequence status selected, an efficiency comparisonof operational savings of boiler operation can be observed anddocumented.

Precision: By observing timely, efficient updates of Boiler Modes andsequencing status, a precise view of the operation of the boiler can beachieve without requiring a separate trip to the boiler room.

Enhancements: Related products can add new features that depend on themode behavior such as state monitors, dial in tools to bus, andcombinations product that would combine for instance VFD efficiency andair/fuel ratio tuning.

Although a separate state controller and flame safety control mechanismis presumed to already exist in the boiler flame safety controller, thebest location for the logic is in the BIC temperature controller andsequencer, where access to open system communications, sequencingcontrols, temperature control, and programming schedule informationresides. The BIC implementation allows for all of the invention'sfeatures described above.

Boiler systems that utilize a number of modular boilers require acontrol system that provides for the sequencing of the modular boilers.Certain aspects of fault tolerant multi-node stage sequencing controller200 were partially explained in relation to arbitration logic module 102a in the explanation of the use of HIP 100 with multiple boilers. Theoperation of sequencing controller 200 may be represented as illustratedin FIG. 5 including a Sequencer Node 300 and a stage node 380. Sequencernode 300 is a temperature control device that monitors the systemcontrol temperatures and makes decisions to actively managemultiple-stage node analog control level and on/off stage decisionschanges such as and adding and removing functioning stages. Sequencernode 300 includes sequencer 302, Runtime & Mode Stage Controller 304,Stage Status Array 306, temperature controller 308, stager 310, analogstage control 312, mode controller 314, and Network Interface 316. Inoperation, temperature controller 308 provides firing rate temperaturedemand signal 320 to analog stage controller 312 and stage temperaturedemand signal 322 to stager 310. Sequencer module 302 receives number ofstages required signal 324 from stager 310 and provides sequencinginformation signal 326 to runtime and Mode stage controller 304. Modecontroller 314 receives temperature control status signal 328 andprovides mode status signal 330. Mode controller 314 provides modestatus signal 332 to runtime and mode stage controller 304 and modesignal 334 to network interface 316. Analog stage controller 312provides firing rate system signal and status signal 336 to runtime modestage controller 304. Stage status array 306 receives stage number andfiring rate signals 338 from runtime and mode stage controller 304 andprovides stage status signal 340 to controller 304. Stage status array306 receives boiler identification (ID), mode and run time informationsignal 342 from interface controller 316 and provides communicationsformatted signal 344 to controller 316.

Stage Node 330 is an active communications and control node thatinterfaces to an active energy source. In the context of boiler systems,stage node 330 may be a boiler interface controller such as BIC 10 thatinterfaces to a flame safety controller 30 and to various sensors,boiler safeties and status signals as previously described herein. Stagenode 330 implements decisions made in sequencer node 300 algorithms forcontrol relating to analog firing rate and the addition or deletion of astage. Information on runtime, control status, and safeties iscommunicated back to Sequencer Node 300.

The present invention is a multi-node sequencing controller (based onstage runtime), which uses the runtime and node stage controller pieceto process unique data-collecting information stored in the stage dataarray. Though the use of the decision technique implemented in theruntime and mode stage controller, operations and total runtime hoursfrom the modular stages are reflected in decisions to request controlactions for the modular heat units in the system. This allows dynamicload balancing as problems affect single and multiple modular heatingnodes.

Sequencing controller 200 provides a method to control dynamic loadingand staging of boiler stage node functionality such as mode progressionmonitoring, pre-purge speed, pre-ignition speed control, Heat evaluationmode, and post purge ignition shutdown capabilities. By proper boilersystem design, all mode monitoring and transitions present in the stagenode can be implemented without interfering with the sequencer nodesstaging requests. In addition, if any errors or faults occur in stagenode 380, then sequencer node 300 can dynamically adjust the control ofthe remaining multiple stages individually of a high efficiencycondensing, automatic bypass control, modulating firing rate boiler bytaking into account the failed status and readjusting the loaddynamically independent of the source control algorithm.

Referring to FIG. 6, periodically sequencer 200 broadcasts a nvoSeqSharemessage 286 globally to all the nodes, however each nvoSeqShare messageis intended for a specific node address and the message contains thisspecific node address. Similarly all stage nodes broadcast theirnvoModBoilerShare message 288 back to sequencer 200 where the message isdecoded. Sequencer node 300 uses an efficient array to collect and rankboiler interface controllers based on the runtime and mode stagecontroller. A more complete understanding of the Sequencer invention maybe obtained from Pseudocode included as an Appendix and the followinginformation regarding data structure herein.

Data structure 1, Stage Array [0 to 16] in Sequencer

Values Percent heat stage 0 to 100% Actual Heat % from stage Heat stageruntime 0 to 65534 hrs. Number of hours from stage Heat stage add rank 0to 16 See note 1 Heat stage del rank 0 to 16 See note 1 Note 1 Heatstage combination Resultant Action add rank = !0, del rank = 0 Off Stage!0 means not 0 add rank = 0, del rank = !0 On Stage !0 means not 0 addrank = 0, del rank = 0 Stage disabled, Invalid or Offline add rank = !0,del rank = !0 Invalid, will be reset to add rank = 0 and del rank = 0

Data structure 2 and data structure 3 are shown in tables 3 and 4respectively.

TABLE 3 Example Data Field Field Field Name (Range) Length Data TypeDescription nvoSeqShare: ShareTempHeat 45% 2 bytes SIGNED LONG ShareTemperature From Cmd (0 to 100%) Heat Command - Sequencer to OutputModular Boiler Command of Nodes heat to modular (nviSeqShare) boilerModularBlrID 3 1 bytes UNSIGNED ID# of Mod INTEGER boiler for which thiscommand is intended ApplicMode HEAT = 9 1 byte ENUMERATION CurrentApplication (See table 1 (BYTE) Mode to be for list of of type commandedto Enumerations) STATUS_MODE the boiler - See Table 1 for possiblevalues Stage Enable ON = 1 1 byte UNSIGNED INT Stage Enable/disablecommand to be commanded to the boiler

TABLE 4 Example Data Field Field Name (Range) Length Data Type FieldDescription NvoModBoiler- BoilerMode HEAT 1 byte ENUMERATION CurrentApplication Share: (See table 1 for (BYTE) Mode of modular From Modularlist of of type boiler. See Table 1 Boiler to Enumerations) STATUS_MODEfor possible values Sequencer Stage Enable ON, 100% 2 byte SNVT_SWITCHStage Enable/disable (nviModBoiler command to be share) commanded to theboiler ModularBlrID 3 1 bytes UNSIGNED ID# of Mod boiler for INTEGERwhich this command is intended ModBlrAlarm ON 1 byte ENUMERATION CurrentAlarm Mode (BYTE) of the modular boiler. Enumeration to be definedcustomer for boiler application BoilLoad 45% 2 bytes SIGNED LONG ActualMod Boiler (0 to 100%) firing rate - BoilerRunTim 250 hrs (0 to 2 bytesUNSIGNED Number of hours that eHr 65535 hrs) LONG this modular boilerstage has run.

The pseudocode contained in the Appendix illustrates a sequence referredto as Efficiency Optimized with Runtime. This Sequence provides atechnique for adding capacity by turning on a boiler having the lowestruntime and reducing capacity by turning off a boiler having the highestruntime. It will be apparent that using the principles of the presentinvention, variations or options may be implemented. For example oneoption could employ a first on/first off sequence as capacity isreduced. Another option could employ operating boilers at a capacitythat is most efficient. For example, if the highest efficiency occurs atminimum loading, then this option would add a boiler when the load issuch that the added boiler can run at minimum capacity. For example, ifboiler number 1 reaches a 60% load, then boiler number 2 could be addedsuch that both boilers can operate at 30% loading. Other variations willbe apparent to those of ordinary skill in the art.

This invention has applications to analog staged energy systems withfault tolerant and transparent dynamic load distribution based on stagestatus and runtime.

While Sequencer 200 has been described in terms of its application to aboiler control system or hot water system it is not limited to theseuses. Sequencer 200 may be used to stage other energy systems, forexample water chillers or electric generators.

The self-configuration invention, an automatic self-configurationtechnique, will now be described. This technique acts in place of anetwork configuration tool such that it provides status and informationto be transferred from client nodes back to a designated supervisorynode so that proper operation can take place without the use of aconfiguration tool. This technique represents substantial value as aself-configuration technique for automatic node addressing andself-configuration for multi-node Supervisory/Client control systems.Referring to FIG. 19, a diagram illustrating self configurationtechnique 400 is shown including a supervisory node 402, client node404, client node 406, client node 408 and client node 410. Additionaldetails of the self-configuration invention are provided in Table 5. Ingeneral nvoClientID could replace the functionality of nvoSupvShare andassign the client nodes to a client ID.

TABLE 5 Network Variable Field Description Example Data Field LengthData Type nvoSupvShare: NID field [6] 00 01 5D 4F 11 26 6 bytes HEX fromSupervisor ui Client Cmd S4 45% 2 bytes UNSIGNED Controller to Client ID3 1 byte UNSIGNED Client Nodes applic Mode HEAT 1 byte ENUM of type(assigns client STATUS_MODE nodes to a client Effective Occ Occ 1 byteSNVT_OCCUPANCY ID) Node Enable ON 1 byte ENUM nvoClientShare: ClientMode HEAT 1 byte ENUM of type from Client to STATUS_MODE Supervisor NodeEnable ON 1 byte ENUM Controller Client ID 3 1 byte UNSIGNED EffectiveOcc Occ 1 byte SNVT_OCCUPANCY ALARM ON 1 byte ENUM ui Client Load S4 44%2 bytes UNSIGNED nvoClientID: NID field [6] 00 01 5D 4F 11 26 6 bytesHEX (OWN NID) periodically Client ID 3 1 byte UNSIGNED broadcast from 1to FE Client ID from Client to Supervisor Client to Ø→ sending fromSupervisor (optional Ø to Supervisor FE) to Client (broadcast client'sneuron ID for collection by supervisor)

This invention resides in the Node firmware portion of the controlsystem and provides for binding of a minimally configuredsupervisory/client control node system.

Supervisory Node/Client Node Binding & Configuration Procedure

1. The firmware in the client nodes is the same as the firmware in thesupervisory node.

2. Initially all nodes are pre-configured identically at the factorydefault values.

3. Initially nvoSupvShare of all nodes are bound to nviSupvShare of allnodes in a group, and nvoClientID of all nodes is bound to nviClientIDof all nodes in a group

4. All nodes have the same domain/subnet/node addresses with theclone_domain-bit set

5. By the use of a digital or analog input, the node with a short(digital) or resistive value set (analog) to a fixed special value atthe input, node 402 is identified as the supervisory node. The internalprogramming of the controller automatically changes the configurationparameter network variable nciConfig. Application Type to Type“Supervisory Node to 16 nodes”—providing nci ConfigSrc is set toCFG_LOCAL showing that no configuration tool has changed anyconfiguration parameters. 6.

Periodically (every 30 seconds) the individual client nodes broadcastsnvoClientID to the supervisory node nviClientID. Other clients alsoreceive nviClientID but ignore nviClientID. NvoClientID containsnviClientID.NIDOut (a 6-character NID string) and the ClientIDOut fieldwhich contains the Client ID (0-254) of the client node. Initially allthe client Ids are set to 0 (unconfigured).

7. All non-supervisory Nodes discard the nviClientID information, butthe Supervisory stores the nvoClientID information into and array andsorts them by NID (Neuron ID). For example:

 Sequence Array [0].NID=00 OF 30 FF 1C 00 Sequence Array [0] .rank=1

 Sequence Array [1].NID=00 OF 31 FF 1C 00 Sequence Array [1] .rank=3

 Sequence Array [2].NID=00 OF 31 FF 1F 00 Sequence Array [2] .rank=2

 Sequence Array [3].NID=00 FF 31 FF 1F 00 Sequence Array [3] .rank=4

8. Supervisory node 402 periodically broadcasts nvoSupvShare tonviSupvShare of all nodes. nvoSupvShare contains a field to identify theNID and its ClientID (the index of the array). The supervisory nodereceives nviSupvShare but ignores nviSupvShare. Client nodes respond tothe nvoSupvShare broadcast if the NID matches their own Neuron ID (setin by the manufacturer of the neuron integrated circuit). 9. At theclient node, if the NID matches its own node, the new ClientID will beupdated to match the new ClientID assigned to it. This involves changingthe Subnet/Node assignment also so that the Subnet is fixed to 1 and theNode is set to the same as the ClientID. From now on, when the clientnode broadcasts nvoClientID, the ClientID will use the ClientID assignedto it by the supervisory node.

10. Optionally, other feedback and status of the Client node isBroadcast (via nvoClientShare) back to the Supervisory node to give apositive ID status of the client ID, the Client state and the clientanalog value.

Control systems that utilize a number of client nodes with individualinterfaces to the client controllers require a control system thatprovides for the coordination of the client nodes. Supervisory node 402and the individual client Controllers 404, 406, 408, and 410 must beconfigured so that communication can occur between supervisory node 402and the individual clients.

All nodes in this invention are initially factory-configured as“clone-domain”, and Echelon LonWorks attribute indicating a special modewhere unique subnet and nodes IDs are not necessary for communication,thus allowing a single configuration to be used to communicate to allother nodes through the same domain.

A single manufactured node type is allowed to be used in both theSupervisor and the individual client node identified as Client 1 toClient 16. Supervisory node 402 is self identified by means of a shortedconfiguration identification input, and client nodes 404, 406, 408, and410 are assumed identified by means of the lack of the presence of theshorted configuration identification input. The binding is simply threesets of network variables, called:

nvoClientID and nviClientID

nvoSupvShare and nviSupvShare

nvoClientShare and nviClientShare

Individual fields within the network variables are identified inFIG._(—)

Periodically, Each individual node nvoClientID is broadcast globally toall the nodes. All non-Supervisory nodes discard the message, but thesupervisory node uses a predefined array to collect, rank and assign anindividual boiler's unique identifier (called NID or Neuron ID). Theunconfigured client node will broadcast a client ID of “00”. TheSupervisory will broadcast a boiler ID of “FF.”

Internally, the Supervisory node's client number ranking is nowbroadcast (via nvoSupvShare) on the clone domain to all the nodes found,including itself. Only the client nodes are programmed to listen to theNID that matches its own node, and subsequently internalize the ClientID and optional analog value commands including mode, analog value, andoccupancy status. The process of internalizing the client ID may includeinternal changes such as updating unique binding and configurationassignments associated with the client node.

Upon reception of the Client ID assignment for the node, the newnvoClientID from the client nodes will broadcast a client ID of “XX,”where XX represents the client ID number of that node.

Other feedback from the client node is broadcast (via nvoClientShare ornvoClientID) back to the Supervisory to give positive identificationstatus of the Client ID, the Client State, and analog value.

The self-configuration technique of the present invention hasapplications to an unknown quantity Supervisory/Client node system toprovide self-configured, automatic addressed, multi-stage-modulatingcontrol.

Another aspect of the Human Interface Panel 100 of the present inventioninvolves the display of boiler status information on a menu level.

The traditional method of displaying user point information and groupingstructures as shown in FIG. 21 involves navigating a user menu withdescriptions. The menus conform to a hierarchical directory structurewith a menu structure of organization eventually ending in a selectionthat reveals point description and values on a multi-line text screen.For an example, a user at a text-based terminal could Select theMechanical room menu 2 and receive a List of selections includingSequencer, Boiler #1, and Boiler #2. After selecting item 1-Sequencer,the point information for the sequencer, i.e., point information items1-5, which relate only to the Sequencer would be displayed.

HIP 100 provides for displaying selective controller information incombination with the Menu choice of controller, for example Sequencer,Boiler #1, Boiler #2. The selective information from the controller iscombined with the logical controller name information (Sequencer, Boiler#1, and Boiler #2) and results in a “concentration” of information fromthe associated boiler. To address the need for a low cost display, thepoint information must be relatively short (small number of characters)and must be able to be displayed in a short space, appropriate for asmaller LCD screen terminal device.

HIP 100 provides for combining information from a number of controllers.With reference to FIG. 22, where the controller name, Boiler #1(available from the node variable for Boiler #1 as nciDevicename) iscombined with the Boiler Status variable “nvoBoilerStatus.ApplicMode”.Optionally, the additional information from nvoFiringRate could be alsoincluded in the result.

For example, 2.ModBlr#01—Heat 17% would be an aggregation of 3 parts:

the first part is the Boiler#1 nciDevice name or boiler node name storedin the boiler interface controller which is “ModBlr#01”, the second partis the Boiler #1 nvoBoilerStatus.ApplicMode value which is “Heat”, andthe third part is the Boiler #1 nvoData.firingRate value which is 17%.

The nvBoilerStatus data Structure is shown in Table 6.

TABLE 6 Example Data Field Field Name (Range) Length Data Type FieldDescription NvoBoilerStatus: ApplicMode HEAT 1 byte ENUMERATION CurrentApplication Polled From (See table 1 (BYTE) Mode of to be Boiler to HIPor for list of of type commanded to the monitoring node Enumerations)STATUS_MODE boiler - See Table 1 for possible values Additional . . . .. . . . . . . . fields Additional . . . . . . . . . . . . fields

Each choice of the Sequencer, Boiler #1, and Boiler #2 represent pointinformation from different controllers. The Boiler Status displayvariable is a result of an arbitration of many different operating andfailure modes, resulting in an extremely useful and pertinentinformation status on the boiler. The result of this synthesis ofgrouping structures and boiler system status information/firing rate inone menu allows dense; information disclosure of 48 arbitrated operatingmode and firing rate information on a controller. Enumerations of theBoiler Status Information variable structure are listed in Table 1.

As implemented in HIP 100, the system level menu of FIG. 22 is theprimary display associated with the Boiler System.

The meaning of the system level information on a line by line basis maybe explained as follows:

Line 1. Sequencer—Heat2Stg-33% - - -

In this example, a Sequencer is sequencing 3 modular boilers. TheSequencer menu displays the Sequencer Status mode in the Heat producingstage, requesting 2 modular boiler for heat with a total system demandof 33% of capacity:

Line 2. ModBlr#01—Heat17%

The sequencer is requesting Boiler #2 to produce heat at 17% of capacityand is functioning normally in the Heat Mode.

Line 3. ModBlr#02—LoGasFail 0%

Modular Boiler #2 is being requested to produce heat by the sequencer,however due to a low gas pressure condition, the boiler is not firing.The firing rate is 0% due to the failure mode. If the HIP operator wasknowledgeable about the system firing rate request information, the usercould have noticed that the system request is for 33% firing rate, andthe first stage is request 17%, leaving 15% load for the 2^(nd) stage.

Line 4 ModBlr#03—Idle 0%

The Sequencer is not requesting this stage to produce heat, and thisstage is off. It is active and has no problems, so it is in the “idle”mode waiting for a request for heat signal from the sequencer.

The Boiler repair person could view the system level view just describedand take additional steps such as the following: verify that the gassupply is available; call the gas company to see if the gas supply tothat boiler has been turned off; and perform or view other diagnosticinformation before traveling to the boiler location.

The information and organization of this rich content menu system forboilers results in reduce troubleshooting time, additional operationinformation, and reduced cost through fast and proper diagnosis of aboiler system problem.

The method used in HIP 100 for displaying information offers manyadvantages, some of which have been described. In addition, it providesquick viewing of a boiler node status without the user being overwhelmedwith information at the point level. System boiler information istypically viewable on one screen. The method provides for easynavigation at a system level to nodes that require more attention orhave problems. Significant diagnostics abilities are provided thoughmonitoring at the “system level” view. By viewing of the data at thesystem level menu, a system perspective of the performance and problemscan be observed without ever taking the time to view the individualpoint information screens for the sequencer and 3 modular boilers.

Thus, since the invention disclosed herein may be embodied in otherspecific forms without departing from the spirit or generalcharacteristics thereof, some of which forms have been indicated, theembodiments described herein are to be considered in all respectsillustrative and not restrictive. The scope of the invention is to beindicated by the appended claims, rather than the foregoing description,and all changes which come within the meaning and range of equivalencyof the claims are intended to be embraced therein.

APPENDIX PSEUDOCODE FOR SEQUENCING RUNTIME (Turns on lowest runtime)(Turns off high runtime)

We claim:
 1. A system of controllers acting as nodes on a network andproviding automatic self configuration comprising: a first node havingmeans for broadcasting a default identifier in a default domain; meansfor designating said first node as a supervisory node; a plurality ofsecond nodes with each second node being a client node and having meansfor broadcasting a default identifier in said default domain; acommunication medium coupling said supervisory node and each said clientnode; means at said first node for receiving and ranking said defaultidentifier from each said client node; means at said first node forcreating a network address for each said client node and communicatingsaid network address in said default domain; and means at each saidclient node for receiving and internalizing said assigned networkaddress thereby enabling communication of control information betweensaid supervisory node and each said client node in a domain that is notsaid default domain.
 2. The system of claim 1 wherein said means fordesignating said first node as a supervisory node comprises a selectedelectrical connection at said first node.
 3. The system of claim 1wherein said default domain allows communication between nodes withoututilizing a subnet and node address.
 4. The system of claim 1 whereinsaid network address in a domain that is not said default domaincomprises a subnet and node address.
 5. The system of claim 1 whereinsaid network utilizes a LonWorks protocol and said nodes areNeuron-based nodes.
 6. The system of claim 5 wherein said firstidentifier comprises a Neuron ID.
 7. The system of claim 1 wherein saidcontrol information is selected from the group consisting of analogvalues, status, mode, alarm, and control commands.
 8. The system ofclaim 1 wherein said means at said first node for creating a networkaddress and said means at said each said client node for receiving andinternalizing said assigned network address comprises a technique ofbinding network variables.
 9. The system of claim 6 wherein said meansat said first node for creating a network address and said means at eachsaid client node for receiving and internalizing said assigned networkaddress comprises a technique of binding network variables.
 10. A systemof controllers acting as nodes on a network and providing automaticself-configuration comprising: a first node having means forbroadcasting a default identifier, said first node being addressable ina first domain by a first domain address; means for designating saidfirst node as a supervisory node; a plurality of second nodes with eachsecond node having means for broadcasting a default identifier, eachsaid second node designated as a client node and addressable in saidfirst domain by a first domain address; a communication medium couplingsaid supervisory node and each said client node; means at saidsupervisory node for receiving and storing said default identifier fromeach client node in a predefined array; means at said supervisory nodefor assigning a second identifier to each said client node andcommunicating said second identifier to each said client node; and meansat each client node for changing said first domain address of saidclient node to a network address in a second domain thereby enablingcommunication of control information between said supervisory node andeach said client node.
 11. The system of claim 10 wherein said firstdomain allows communication between nodes without a subnet and nodeaddress.
 12. The system of claim 10 wherein said network address in asecond domain comprises a subnet and node address.
 13. The system ofclaim 10 wherein said control information is selected from the groupconsisting of analog values, status, mode, alarm, and control commands.14. The system of claim 10 wherein said means for designating said firstnode as a supervisory node comprises a selected electrical connection atsaid first node.
 15. The system of claim 10 wherein said networkutilizes a LonWorks protocol and said nodes are Neuron based nodes. 16.The system of claim 10 wherein said means at said supervisory node forcommunicating said second identifier and said means at said each saidclient node for changing said first domain address of said client nodeto a network address in a second domain comprises a technique of bindingnetwork variables.
 17. The system of claim 15 wherein said defaultidentifier for a second node comprises a Neuron ID.
 18. A method ofconfiguring controllers to allow communication on a network comprisingthe steps of: providing controllers, with each controller having a firstidentifier and being configured from a default value to communicate saidfirst identifier; designating one controller as a supervisory node;designating each remaining controller as a client node; connecting saidsupervisory node and each remaining controller to a network;initializing operation of said controllers; communicating said firstidentifiers; storing said first identifiers in an array at saidsupervisory node, with said first identifiers stored according to acharacteristic contained in said first identifiers; and assigning asecond identifier to each remaining controller, said second identifierenabling said supervisory node to communicate control information; andcommunicating control information between said supervisory node and eachremaining controller.
 19. The method of claim 18 wherein said step ofdesignating one controller as a supervisory node comprises the step ofmaking an electrical connection at said one node.
 20. The method ofclaim 18 wherein said step of assigning a second identifier comprisesassigning subnet node addressing.
 21. The method of claim 18 whereinsaid step of communicating control information comprises communicatinginformation selected from the group consisting of analog values, status,mode, alarm, and control commands.
 22. The method of claim 20 whereinsaid network utilizes a standard communication protocol.
 23. The methodof claim 22 wherein said standard communication protocol is LonWorks.